apps/atrium-telegram/app/app.vue (1)

96-96: Consider the impact of reduced refresh interval.

The refresh interval has been reduced from 30 seconds to 20 seconds. While this provides more frequent updates, it increases server load and client battery consumption.

-  }, 20000)
+  }, 30000)

Consider whether the 10-second reduction is necessary, or if adaptive polling based on user activity would be more efficient.

apps/atrium-telegram/app/components/TicketCard.vue (2)

17-17: Fix potential runtime error with optional chaining

The optional chaining on line 17 is inconsistent with the prop type. Since ticket is a required prop of type TicketWithData which guarantees messages is an array, the optional chaining is unnecessary. However, if messages could be undefined in practice, you should use ticket.messages?.length ?? 0 to avoid displaying undefined.

-          <p>{{ ticket?.messages.length }}</p>
+          <p>{{ ticket.messages?.length ?? 0 }}</p>

---

24-24: Consider extracting date format string as a constant

The hardcoded Russian text "обновлен" in the format string makes the component less maintainable and not internationalization-friendly. Consider using the i18n system for this label.

-        v-text="format(new Date(ticket.updatedAt), 'обновлен d MMMM yyyy', { locale: ru })"
+        v-text="`${$t('common.updated')} ${format(new Date(ticket.updatedAt), 'd MMMM yyyy', { locale: ru })}`"

Also add the translation key to your i18n files:

{
  "common": {
    "updated": "обновлен"
  }
}

apps/atrium-telegram/app/stores/ticket.ts (1)

22-24: Consider more explicit handling of empty responses

The current check if (!data) only handles falsy values but doesn't distinguish between an empty array (valid response with no tickets) and an actual error condition. Consider being more explicit about what constitutes a valid response.

-      if (!data) {
-        return
-      }
+      if (!Array.isArray(data)) {
+        console.warn('Unexpected response format from /api/ticket/list')
+        return
+      }

apps/atrium-telegram/app/components/TicketMessage.vue (1)

119-130: Add proper TypeScript type safety for file type parameter

The getFileIcon function accepts a union type including null, but the implementation doesn't explicitly handle the null case (it falls through to default). While this works, it's better to be explicit for clarity and type safety.

-function getFileIcon(type: 'image' | 'video' | 'document' | null) {
+function getFileIcon(type: 'image' | 'video' | 'document' | null): string {
   switch (type) {
     case 'image':
       return 'i-lucide-image'
     case 'video':
       return 'i-lucide-video'
     case 'document':
       return 'i-lucide-file'
+    case null:
     default:
       return 'i-lucide-file'
   }
 }

apps/atrium-telegram/app/pages/ticket/[ticketId]/index.vue (2)

20-20: Handle edge case for undefined ticket in pluralization

The pluralization function receives ticket?.messages.length ?? 0 but the template also references ticket?.messages.length directly without fallback, which could display undefined.

-        {{ ticket?.messages.length }} {{ pluralizationRu(ticket?.messages.length ?? 0, ['сообщение', 'сообщения', 'сообщений']) }}
+        {{ ticket?.messages.length ?? 0 }} {{ pluralizationRu(ticket?.messages.length ?? 0, ['сообщение', 'сообщения', 'сообщений']) }}

---

44-58: Clean up commented code

There's a large block of commented code for a drawer component. If this feature is planned for future implementation, consider adding a TODO comment explaining when it will be implemented. Otherwise, remove it to keep the codebase clean.

Either remove the commented code entirely or replace with a clear TODO:

-    <!-- <UDrawer v-model:open="isDrawerOpened">
-      <CreateCard
-        v-if="epic?.id"
-        :label="$t('app.create.epic-comment.button')"
-        icon="i-lucide-message-circle"
-      />
-
-      <template #body>
-        <FormCreateEpicComment
-          :epic-id="epic?.id ?? ''"
-          @submitted="isDrawerOpened = false"
-          @success="isDrawerOpened = false"
-        />
-      </template>
-    </UDrawer> -->
+    <!-- TODO: Implement comment creation drawer when FormCreateTicketComment is ready -->

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro